home *** CD-ROM | disk | FTP | other *** search
- Path: news.nyu.edu!schonberg!dewar
- From: dewar@cs.nyu.edu (Robert Dewar)
- Newsgroups: comp.lang.ada,comp.lang.c,comp.lang.c++,comp.edu
- Subject: Re: ANSI C and POSIX (was Re: C/C++ knocks the crap out of Ada)
- Date: 10 Apr 1996 15:18:30 -0400
- Organization: Courant Institute of Mathematical Sciences
- Message-ID: <dewar.829163754@schonberg>
- References: <JSA.96Feb16135027@organon.com> <dewar.828936837@schonberg> <4kb2j8$an0@solutions.solon.com> <4kbrt5$k3h@mulga.cs.mu.OZ.AU> <4kcer3$mi4@solutions.solon.com> <4kdnvq$3n8@mulga.cs.mu.OZ.AU> <4kgmgu$jm@galaxy.ucr.edu> <AUSTERN.96Apr10103441@isolde.mti.sgi.com>
- NNTP-Posting-Host: schonberg.cs.nyu.edu
- X-Newsreader: NN version 6.5.0 (NOV)
-
- "Are you sure that this is possible on the machines that you'd like
- your program to run on? On many of today's RISC chips, after all,
- floating point exceptions are asynchronous: you have no way of
- knowing which instruction caused the problem."
-
- Actually, some modern RISC chips effectively do not generate floating-point
- exceptions. The IEEE 754 (floating-point) standard does NOT require this
- capability.
-
- An example is the POWER architecture, where you can only get floating-point
- exceptions by disconnecting the pipeline and slowing down ALL code
- drastically. This mode is intended only or debugging, not for production
- use.
-
- It seems quite reasonable in fact to consider designing floating-point
- feature sets with no capability of asyncrhonous exceptions at all.
-
-